This is a comment left during a code review.
Path: packages/browser/src/posthog-featureflags.ts
Line: 973-983

Comment:
**Duplicated array-to-flags-object conversion**

The `for` loop that converts a string array into a `Record<string, string | boolean>` is now written twice — once here for the top-level array form and again inside the `{ flags: [...] }` branch at lines 999–1004. This violates OnceAndOnlyOnce and means any future change (e.g. trimming flag names, logging) must be applied in both places.

Consider extracting a small helper:

```ts
function arrayToFlagsRecord(flags: string[]): Record<string, string | boolean> {
    const flagsObj: Record<string, string | boolean> = {}
    for (let i = 0; i < flags.length; i++) {
        flagsObj[flags[i]] = true
    }
    return flagsObj
}
```

Then both call sites become a single `arrayToFlagsRecord(...)` call.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: packages/browser/src/__tests__/featureflags.test.ts
Line: 961-995

Comment:
**Prefer parameterised tests**

The first two cases follow an identical structure (call `overrideFeatureFlags` with an input, assert `getFlagVariants()` equals an expected object). Per project convention, these are a good candidate for `it.each`:

```ts
it.each([
    [
        'plain array',
        ['beta-feature', 'alpha-feature-2'],
        { 'beta-feature': true, 'alpha-feature-2': true },
    ],
    [
        'plain object',
        { 'beta-feature': 'variant-1', 'alpha-feature-2': false },
        { 'beta-feature': 'variant-1', 'alpha-feature-2': false },
    ],
])('supports %s shorthand form for flag overrides', (_, input, expected) => {
    featureFlags.overrideFeatureFlags(input as any)
    expect(featureFlags.getFlagVariants()).toEqual(expected)
})
```

The third test ("plain object does not affect payloads") checks a distinct concern and is fine as a standalone `it`.

How can I resolve this? If you propose a fix, please make it concise.